Skip to content
This repository has been archived by the owner on Aug 16, 2024. It is now read-only.

ci: sidecar images updates will be also created for latest bugfix branch #434

Closed
wants to merge 2 commits into from

Conversation

mkuznyetsov
Copy link
Contributor

@mkuznyetsov mkuznyetsov commented Jun 30, 2021

Signed-off-by: Mykhailo Kuznietsov [email protected]

What does this PR do?

When we create updates for sidecar images into main branch, they must be also cherry-picked into bugfix branch (as bugfix releases will remain broken otherwise). With this PR, the job will also create PR for latest bugfix branch

Screenshot/screencast of this PR

What issues does this PR fix or reference?

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

@@ -77,6 +88,7 @@ if [[ $(git diff --exit-code "${SCRIPT_DIR}"/base_images) ]]; then
else
echo "[INFO] Changes detected, generating PR with new digests"
createPR "new-base-image-digests"
create
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops

@@ -72,4 +72,5 @@ jobs:
git config --global user.name "Mykhailo Kuznietsov"
git config --global user.email "[email protected]"
export GITHUB_TOKEN=${{ secrets.CHE_BOT_GITHUB_TOKEN }}
./arbitrary-users-patch/check_sidecar_image_digests.sh
BUGFIX_BRANCH="$(git branch -a | grep "remotes/origin/7.*" | cut -d '/' -f 3 | sort --version-sort | tail -n1)"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if a topic branch is created called 7.32.x-some-reason? will that be used instead of 7.32.x ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, I should add protection from that

@ericwill
Copy link
Contributor

ericwill commented Jul 5, 2021

We are planning to decouple the dev container images from the Che release lifecycle, so I'm not sure how much more time you want to invest in this PR.

@nickboldt
Copy link
Contributor

@ericwill are you saying this PR is now moot? If so, feel free to just close it and add a comment on its related issue: eclipse-che/che#19695

@nickboldt
Copy link
Contributor

image

@nickboldt nickboldt closed this Jul 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants